The test failures are expected, at least until engines update their Unicode data to v17.

We talked in the maintainers meeting and think the right time frame for merging this is 1 month after CLDR 48 is released.

They didn't do a timely update of the release notes which still say beta draft but the final version of CLDR 48 was released on October 23: https://github.com/unicode-org/cldr/releases/tag/release-48

A month has passed so this and #4572 can be merged.

Additionally I'd like to point out that there's a circular dependency here - engines might not want to update their version of CLDR before relevant tests have landed, e.g. quickjs-ng/quickjs#1168. Perhaps it makes sense to treat this similar to stage 2.7 and merge tests before asking implementations to update in the future.

Additionally I'd like to point out that there's a circular dependency here - engines might not want to update their version of CLDR before relevant tests have landed, e.g. quickjs-ng/quickjs#1168. Perhaps it makes sense to treat this similar to stage 2.7 and merge tests before asking implementations to update in the future.

+1 to this. In the past, we landed these updated tests as soon as they became available, and IMHO we should get back to that.

I'm assuming the ESMeta test failures are because of ESMeta not having updated Unicode data.